Architecture for managing I/O and storage for a virtualization environment using executable containers and virtual machines

ABSTRACT

Systems for high-performance computing. A storage control architecture is implemented by a plurality of nodes, where a node comprises combinations of executable containers that execute in cooperation with virtual machines running above a hypervisor. The containers run in a virtual machine above a hypervisor, and/or can be integrated directly into the operating system of a host node. Sensitive information such as credit card information may be isolated from the containers in a separate virtual machine that is configured to be threat resistant, and which can be accessed through a threat resistant interface module. One of the virtual machines of the node may be a node-specific control virtual machine that is configured to operate as a dedicated storage controller for a node. One of the virtual machines of the node may be a node-specific container service machine that is configured to provide storage-related and other support to a hosted executable container.

RELATED APPLICATIONS

The present application is a continuation application of U.S.application Ser. No. 15/173,577 titled, “ARCHITECTURE FOR MANAGING I/OAND STORAGE FOR A VIRTUALIZATION ENVIRONMENT USING EXECUTABLE CONTAINERSAND VIRTUAL MACHINES”, filed on Jun. 3, 2016, which claims the benefitof priority to U.S. Patent Application Ser. No. 62/171,990 titled,“ARCHITECTURE FOR MANAGING I/O AND STORAGE FOR A VIRTUALIZATIONENVIRONMENT USING CONTAINERS AND VIRTUAL MACHINES”, filed Jun. 5, 2015,which are hereby incorporated by reference in its entirety.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD

This disclosure relates to high-performance computing and moreparticularly to techniques for managing executable containers in avirtualization environment.

BACKGROUND

The term “virtualization” has taken on many meanings in the domain ofcomputers and operating systems as well as in storage and networkingdomains. Hardware (e.g., CPUs and peripherals) can be virtualized so asto “hide” the details of how to interface with the hardware from a userby adding a layer of software (e.g., an operating system). Likewise, anoperating system can be virtualized so as to “hide” the details how tointerface with the operating system by adding a layer of software (e.g.,a hypervisor). Users can write code to perform some functions without astrong reliance on the underlying infrastructure such as a particularoperating system and/or a particular vendor and/or a particularconfiguration of hardware.

Further, details pertaining to interfacing with underlying storagefacilities and networking configurations can be abstracted by providinga specially configured “control” virtual machine (see below), and userscan write code that runs in another “user” virtual machine. Suchabstractions are a boon to code developers and system administratorsalike, and very large virtualized systems comprising many hundreds orthousands of nodes and many hundreds or thousands (or millions) of uservirtual machines can be configured and managed by an operator whointerfaces with a configuration panel to configure said hundreds orthousands (or millions) of virtual machines.

In a virtualized system, it is sometimes convenient for a developer todeploy some set of functions using units called “containers”. Acontainer can be configured to implement a particular function withoutreliance of a fully-configured hardware and/or software platform. Forexample, a container might be defined to perform some simple operationover some inputs and produce an output. In such a case, the containermight be very lightweight, requiring only a way to receive the inputs, away to perform the simple operation, and a way to provide the output.The “weight” of a hypervisor and/or an operating system is unnecessaryin this case. In some cases a container might be defined to provide asomewhat more complex service, in which case the developer of thecontainer might choose to bring some small portion of an operatingsystem or hypervisor into the container. In such a case, the resultingcontainer can still be lightweight vis-à-vis the alternative of bringingin the entire operating system or hypervisor. In still more situations,a group of containers might be defined and developed in such a mannerthat the group of containers performs as an “application”. This paradigmcan be extended to include many hundreds or thousands (or millions) ofcontainers.

Virtualization Using Virtual Machines

A “virtual machine” or a “VM” refers to a specific software-basedimplementation of a machine in a virtualization environment in which thehardware resources of a real computer (e.g., CPU, memory, etc.) arevirtualized or transformed into the underlying support for the fullyfunctional virtual machine that can run its own operating system andapplications on the underlying physical resources just like a realcomputer. Virtualization works by inserting a thin layer of softwaredirectly on the computer hardware or on a host operating system. Thislayer of software contains a virtual machine monitor or “hypervisor”that allocates hardware resources dynamically and transparently.Multiple operating systems run concurrently on a single physicalcomputer and share hardware resources with each other.

Virtualization Using Container-Based Virtualization

Recently, container-based virtualization technologies have grown inpopularity. In comparison to virtual machines, which mimic independentphysical machines by creating a virtual machine that runs on top of ahost's operating system, containers virtualize the applications that canrun in user-space directly on an operating system's kernel.Applications, such as a web server or database that run from within acontainer, do not require an emulation layer or a hypervisor layer tointerface with the physical machine. Instead, “containerized”applications can function using an operating system's normal systemcalls. In this way, containers provide operating system-levelvirtualization that is generally faster (e.g., faster to transport,faster to “boot” or load) than virtual machines because the containersdo not require virtualized guest OSes.

One reason for the broad adoption of virtualization technologies such asvirtual machines or containers is the resource advantages provided bythe virtual architectures. Without virtualization, if a physical machineis limited to a single dedicated operating system, then during periodsof inactivity by the dedicated operating system the physical machine isnot used to perform useful work. This is wasteful and inefficient ifthere are users on other physical machines that are currently waitingfor computing resources. In contrast, virtualization allows multiplevirtualized computers (e.g., VMs, containers) to share the underlyingphysical resources so that during periods of inactivity by onevirtualized computer, another virtualized computer can take advantage ofthe resource availability to process workloads. This can produce greatefficiencies for the use of physical devices, and can result in reducedredundancies and better resource cost management.

Data centers are often architected as diskless computers (“applicationservers”) that communicate with a set of networked storage appliances(“storage servers”) via a network, such as a fiber channel or Ethernetnetwork. A storage server exposes volumes that are mounted by theapplication servers for their storage needs. If the storage server is ablock-based server, it exposes a set of volumes by logical unit numbers(LUNs). If, on the other hand, a storage server is file-based, itexposes a set of volumes called file systems.

While generally more lightweight than VMs, containers that areimproperly secured can provide malicious access (e.g., root access) to aphysical host computer running the containers. Further, containertechnologies currently do not provide a means for storage optimizationsto occur in the primary storage path. Generally, containers areintegrated directly with the operating system (OS) to work with thekernel using system calls. Optimizing storage for containers can requireheavy OS customization. Compounding these issues and problems endemic tocontainer technologies, deployment of containers in virtualizedenvironments brings a raft of hitherto unaddressed problems.

Unfortunately, legacy techniques to integrate and control containers ina virtualized environment have fallen short. Indeed, although containerscan be deployed and managed in rudimentary ways using legacy tools, suchlegacy tools fall far short of providing the comprehensive set ofconfiguration, deployment, and publishing features that are demanded inhyper-converged platforms. What is needed is a way for one, or tens, orhundreds, or thousands, or millions of containers to be deployed andcontrolled in a virtualized environment.

What is needed is a technique or techniques to improve over legacyand/or over other considered approaches. Some of the approachesdescribed in this background section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

SUMMARY

The present disclosure provides a detailed description of techniquesused in systems, methods, and in computer program products for managingexecutable containers in virtualization environments, which techniquesadvance the relevant technologies to address technological issues withlegacy approaches. More specifically, the present disclosure provides adetailed description of techniques used in systems, methods, and incomputer program products for managing containers in a virtualizationenvironment. Certain embodiments are directed to technological solutionsfor provide a deployment and configuration layer that interfaces withany number of containers.

The disclosed embodiments modify and improve over legacy approaches. Inparticular, the herein-disclosed techniques provide technical solutionsthat address the technical problems attendant to deploying, and managinglarge numbers of containers a hyper-converged virtualizationenvironment. Such technical solutions serve to reduce the demand forcomputer memory, reduce the demand for computer processing power, reducenetwork bandwidth use, and reduce the demand for inter-componentcommunication. Some embodiments disclosed herein use techniques toimprove the functioning of multiple systems within the disclosedenvironments, and some embodiments advance peripheral technical fieldsas well. As one specific example, use of the disclosed techniques anddevices within the shown environments as depicted in the figures provideadvances in the technical field of high-performance computing as well asadvances in various technical fields related to data storage.

Further details of aspects, objectives, and advantages of thetechnological embodiments are described herein and in the drawings andclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings described below are for illustration purposes only. Thedrawings are not intended to limit the scope of the present disclosure.

FIG. 1A and FIG. 1B illustrate example virtualized computers as used formanaging containers in a virtualization environment, according to someembodiments.

FIG. 1C illustrates an example container on bare metal.

FIG. 1D1, FIG. 1D2, FIG. 1D3, FIG. 1D4 and FIG. 1D5 depict blockdiagrams of a container support system used for configuring, deploying,and managing containers in a virtualization environment, according to anembodiment.

FIG. 1E presents a flowchart of an environment preparation technique asused by administrators in systems for configuring, deploying, andmanaging containers in a virtualization environment, according to anembodiment.

FIG. 1F presents a flowchart of a multi-phase workflow as used byadministrators and developers in systems for configuring, deploying, andmanaging containers in a virtualization environment, according to anembodiment.

FIG. 1G presents a flowchart of a container-to-node mapping technique asused in systems for configuring, deploying, and managing containers in avirtualization environment, according to an embodiment.

FIG. 1H and FIG. 1I present a flowcharts of storage pool use models,according to some embodiments.

FIG. 2 illustrates an example cluster architecture as used to implementI/O and storage device management in systems that support cluster-wideconfiguration of containers in a virtualization environment, accordingto an embodiment.

FIG. 3 depicts a single-node container service machine configuration,according to an embodiment.

FIG. 4 illustrates a one-container-service-machine-per-node architectureas used in systems that support cluster-wide configuration of containersin a virtualization environment, according to an embodiment.

FIG. 5 illustrates a one-control-virtual-machine-per-node architectureas used in systems that support cluster-wide configuration of containersin a virtualization environment, according to an embodiment.

FIG. 6 illustrates a foreign OS architecture as used for runningcontainers on top of a foreign OS in systems that support cluster-wideconfiguration of containers in a virtualization environment, accordingto an embodiment.

FIG. 7A, FIG. 7B1, FIG. 7B2, FIG. 7B3 and FIG. 7C illustrate variousinter-node communication techniques as used in systems that supportconfiguring, deploying, and managing containers in a virtualizationenvironment, according to an embodiment.

FIG. 8 illustrates container uses of VLAN communication techniques asused in systems that support configuring, deploying, and managingcontainers in a virtualization environment, according to an embodiment.

FIG. 9A and FIG. 9B illustrate alternative embodiments of a controlvirtual machine as used within systems for managing containers in avirtualization environment, according to an embodiment.

FIG. 10 depicts system components as arrangements of computing modulesthat are interconnected so as to implement certain of theherein-disclosed embodiments.

FIG. 11A and FIG. 11B depict virtualized controller architecturescomprising collections of interconnected components suitable forimplementing embodiments of the present disclosure and/or for use in theherein-described environments.

DETAILED DESCRIPTION

Some embodiments of the present disclosure address the problem ofdeploying, and managing large numbers of containers a hyper-convergedvirtualization environment and some embodiments are directed toapproaches for provide a deployment and configuration layer thatinterfaces with any number of containers. The accompanying figures anddiscussions herein present example environments, systems, methods, andcomputer program products for managing containers in a virtualizationenvironment.

Overview

Disclosed herein are systems and techniques that serve to integrate andcontrol executable containers within a virtualized environment. Thesystems and techniques discussed hereunder disclose a comprehensive setof configuration, deployment, and publishing features that advanceperformance aspects and features of hyper-converged platforms.

Various embodiments are described herein with reference to the figures.It should be noted that the figures are not necessarily drawn to scaleand that elements of similar structures or functions are sometimesrepresented by like reference characters throughout the figures. Itshould also be noted that the figures are only intended to facilitatethe description of the disclosed embodiments—they are not representativeof an exhaustive treatment of all possible embodiments, and they are notintended to impute any limitation as to the scope of the claims. Inaddition, an illustrated embodiment need not portray all aspects oradvantages of usage in any particular environment.

An aspect or an advantage described in conjunction with a particularembodiment is not necessarily limited to that embodiment and can bepracticed in any other embodiments even if not so illustrated. Also,references throughout this specification to “some embodiments” or “otherembodiments” refers to a particular feature, structure, material orcharacteristic described in connection with the embodiments as beingincluded in at least one embodiment. Thus, the appearance of the phrases“in some embodiments” or “in other embodiments” in various placesthroughout this specification are not necessarily referring to the sameembodiment or embodiments.

Definitions

Some of the terms used in this description are defined below for easyreference. The presented terms and their respective definitions are notrigidly restricted to these definitions—a term may be further defined bythe term's use within this disclosure. The term “exemplary” is usedherein to mean serving as an example, instance, or illustration. Anyaspect or design described herein as “exemplary” is not necessarily tobe construed as preferred or advantageous over other aspects or designs.Rather, use of the word exemplary is intended to present concepts in aconcrete fashion. As used in this application and the appended claims,the term “or” is intended to mean an inclusive “or” rather than anexclusive “or”. That is, unless specified otherwise, or is clear fromthe context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A, X employs B, or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. As used herein, at least one of A or B means atleast one of A, or at least one of B, or at least one of both A and B.In other words, this phrase is disjunctive. The articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or is clearfrom the context to be directed to a singular form.

Reference is now made in detail to certain embodiments. The disclosedembodiments are not intended to be limiting of the claims.

Descriptions of Example Embodiments

FIG. 1A, FIG. 1B, FIG. 1C and FIG. 2 depict computing platformvirtualization environments that support (1) virtual machinearchitectures, (2) executable container architectures and (3) varioushereunder-described combinations of executable containers operating incooperation with virtual machines. In many environments, executablecontainers comprise executable code that interfaces to resources of ahosting computing node. In some cases the executable code can bedeployed as binary code, and/or as byte code, and/or as interpretedcode. The code can interface to resources of a computing node without ahypervisor, and code can interface to the resources of a computing nodewithout reliance on any particular operating system configuration. Instill some other situations, the executable container can subsumeportions of operating system code that interfaces to the resources of acomputing node in a multi-processing mode, where the subsumed operatingsystem code includes portions of an operating system code, such as anoperating system kernel or portion thereof. Executable containers canprovide computing services, possibly including entire applications, andcan operate in many architectures, including virtual machinearchitectures.

The depictions of virtual machine architecture 100 (see FIG. 1A),container architecture 110 (see FIG. 1B), and “bare metal” architecture112 (see FIG. 1C) show examples of how applications or services can bedeployed within the various architectures. Applications or services canbe configured to provide any functionality. For example, an applicationor service can implement a user-defined function, a middleware function,and/or can implement services that interact with the computingenvironment. Such computing environments can include multiple computingnodes, any of which communicate over network facilities. The multiplecomputing nodes can interact with storage facilities such as node-localstorage as well as networked storage.

In many situations as disclosed herein, executable containers operate incooperation with virtual machines. In some cases the executablecontainers might need access to the same or similar storage facilitiesas are accessed by the virtual machines.

Described herein are architectures, configurations, and techniques forimplementing storage management over shared storage facilities. Morespecifically, FIG. 2 illustrates an architecture for implementingstorage management in a clustered virtualization environment. Theexample cluster architecture 200 depicts a multi-node cluster 201 havingtwo nodes that share a common storage pool. The architecture of FIG. 2can implement a distributed platform that contains nodes in the form ofservers (e.g., shown as node 202 ₁ and node 202 ₂) that manage multipletiers of storage in the storage pool 242. The multiple tiers of storageincludes storage that is accessible through a network 240, such as cloudstorage 226 or networked storage 228 (e.g., a SAN or storage areanetwork). Additionally, the present embodiment also permits localstorage 222 ₁ and local storage 222 ₂ that is within or directlyattached to the server and/or appliance to be managed as part of thestorage pool 242 that is shared by a plurality of nodes of the cluster.Examples of such storage include solid-state drives (e.g., solid-statestorage devices 225) or spindle drives (e.g., direct attached storage227), etc. These collected storage devices, both local and networked,form a storage pool 242. Virtual disks (vDisks) can be structured fromthe storage devices in the storage pool 242, as described in more detailbelow. As used herein, the term vDisk refers to the storage abstractionthat is exposed by a control VM to be used by a user VM. In someembodiments, the vDisk is exposed via an internet small computer systeminterface (iSCSI) or a network file system (NFS) and is mounted as avirtual disk on the user VM.

As depicted, each server runs virtualization software such as VMwareESXi, Microsoft Hyper-V, or RedHat KVM, etc. The virtualization softwareincludes a hypervisor (e.g., hypervisor 104 ₄, hypervisor 104 ₅) runningatop an operating system (e.g., operating system 102 ₅, operating system102 ₆) to manage the interactions between the underlying hardware andthe one or more container service machines that run client software.

The one or more instances of a container service machine 150 (e.g.,instances shown as user container virtual machine 250 ₁₁, user containervirtual machine 250 ₁₂, . . . , user container virtual machine 250_(1N)) may be implemented as a virtual machine with an operating system102 ₁ that supports containers (e.g., Linux). As such, one or more usercontainers (e.g., user container 252 ₁₁, user container 252 ₁₂, usercontainer 252 ₁₃, user container 252 ₁₄) may run from within itsrespective user container virtual machine. Each of the user containersmay comprise one or more images that are layered to appear as a singlefile system for that container. For example, a base layer may correspondto a Linux Ubuntu image, with an application execution layer on top. Theapplication execution layer corresponding to a read/write executionenvironment for applications, such as MySQL or websites, is explainedfurther below.

A different node configuration shown as node 202 ₂ can access the samestorage pool 242, even though the node is configured differently fromnode 202 ₁. As shown, the node 202 ₂ comprises one or more instances ofa container virtual machine (e.g., instances shown as user containervirtual machine 250 ₂₁, user container virtual machine 250 ₂₂, . . . ,user container virtual machine 250 _(2N)) which may be implemented as avirtual machine with an operating system 102 ₂ that supports containers.As such, one or more user containers (e.g., user container 252 ₂₁, usercontainer 252 ₂₂, user container 252 ₂₃, user container 252 ₂₄) may runfrom within it respective user container virtual machine.

In some embodiments, special service-virtualized computers, hereillustrated as control virtual machine 130 ₂ and control virtual machine130 ₃, are used to manage storage and I/O activities for the usercontainers. The control virtual machine serves as a “storage controller”in the currently described architecture. Multiple such storagecontrollers coordinate within a cluster to form a single system. Thecontrol virtual machines are not formed as part of specificimplementations of hypervisors. Instead, the control virtual machinesrun as virtual machines above respective hypervisors on the variousshown nodes, and work together to form a distributed system 210 thatmanages all the storage resources, including the locally attachedstorage (e.g., local storage 222 ₁, and local storage 222 ₂) as well asthe networked storage 228 and the cloud storage 226. Since the controlVMs run above the hypervisor, this means that the current approach canbe used and implemented within any virtualized computer architecturesince the control VMs of embodiments of the invention can be used inconjunction with any hypervisor from any virtualization vendor.

Each control VM exports one or more block devices or NFS server targetsthat appear as disks to the user containers. These disks are virtual,since they are implemented by software running inside the control VMs.Thus, to a user container, the control VMs appear to be exporting aclustered storage appliance that contains some disks. Also, all userdata (including the operating system) in the container service machinesresides on these virtual disks.

Significant performance advantages can be gained by allowing thevirtualization system to access and use local, server-internal storage.This is because I/O performance is typically much faster when performingaccess to local storage as compared to performing access to networkedstorage 228 across a network 240. This faster performance for locallyattached storage can be increased even further by using certain types ofoptimized local storage devices, such as SSDs 225, as shown.

Once the virtualization system is configured so as to be capable ofmanaging and accessing locally attached storage, as is the case with thepresent embodiment, various optimizations can then be implemented toimprove system performance even further. For example, the data to bestored in the various storage devices can be analyzed and categorized todetermine which specific device should optimally be used to store theitems of data. Data that needs to be accessed much faster or morefrequently can be identified for storage in the locally attachedstorage. On the other hand, data that does not require fast access orwhich is accessed infrequently can be stored in the networked storagedevices or in cloud storage 226.

Further details regarding approaches for implementing storage managementwithin virtualization environments are described in U.S. Pat. No.8,601,473 titled “ARCHITECTURE FOR MANAGING I/O AND STORAGE FOR AVIRTUALIZATION ENVIRONMENT”, issued on Dec. 3, 2013, which is herebyincorporated by reference in its entirety.

Virtualization environments include computers that execute computercode, the execution of which can emulate or abstract hardware and/orsoftware components for access through one or more abstraction layers.Abstraction layers can take many forms, possibly including hypervisors,application programming interfaces (APIs), libraries, containers,middleware components, etc. Applications and services can access theemulated or abstracted hardware and/or software components through theabstraction layer. In some cases entire computer settings are abstractedso as to isolate the aforementioned applications or services from thedetails of the virtualized hardware and/or software components. Severalapproaches for virtualized computing are now briefly discussed asexample approaches. Some approaches include virtual machines, someapproaches include executable containers, and some approaches includecombinations thereof.

Specifically FIG. 1A and FIG. 1B illustrate approaches for implementingvirtualized computing machines using virtual machines (FIG. 1A) andcontainers (FIG. 1B). In FIG. 1A, a virtual machine architecture 100 isillustrated comprising hardware 101 ₁ which includes the physicalhardware of a computer such as a processor and memory. An operatingsystem 102 ₁ may be installed on the hardware 101 ₁. Further, ahypervisor 104 ₁ may be installed on the operating system to instantiateand manage one or more virtual machines (e.g., virtual machine 106 ₁ andvirtual machine 106 ₂). Though FIG. 1A shows the hypervisor 104 ₁installed on the operating system 102 ₁, in some embodiments ahypervisor 104 ₁ may be installed and function directly from thehardware level (e.g., running on “bare metal”).

The virtual machine 106 ₁ and virtual machine 106 ₂ may each haveoperating systems installed within them (not depicted), such asMicrosoft Windows or Linux. The virtual machines may have allocatedmemory and processor resources from the hardware level. The virtualmachines may be used to run one or more applications, such asapplication 108 ₁ and application 108 ₂.

Though one application per virtual machine is illustrated in FIG. 1A,one of ordinary skill in the art appreciates that each virtual machine(e.g., virtual machine 106 ₁, and virtual machine 106 ₂) may run aplurality of applications in their respective virtualized computingenvironment. While virtual machines provide effective computer securityand flexibility in provisioning resources, in some implementations theymay be unwieldy because a hypervisor layer must still be installed ontothe operating system. Further, each virtual machine might require a fulloperating system, a substantial amount of disk-space, and might consumea significant portion of processor computing power as well as asubstantial amount of memory.

FIG. 1B illustrates an alternative approach for virtualized computingenvironments using containers. There, container architecture 110comprises a hardware 101 ₂ comprising physical hardware, such as one ormore processors (e.g., processor cores) and memory. An operating system102 ₂ is installed on the hardware 101 ₂. The operating system 102 ₂ isconfigured to support containers using container support frameworks suchas Linux containers (e.g., LXC) and Docker (e.g., dockerizedcontainers). Docker is company that provides products (e.g., Docker) fordeployment of code (e.g., services, applications) within a containerexecution environment.

As illustrated, the operating system can host and support or manage oneor more containers, such as container 116 ₁ and container 116 ₂. Thecontainers may implement one or more applications as containerizedapplications, such as application 108 ₃ and application 108 ₄. Notably,containerized applications can run directly from the operating system ina container without a hypervisor layer or dedicated memory, disk space,or processors. This containerized approach allows containers to berelatively lightweight as each application can run without a fullvirtual machine (VM) running. Although only one application isillustrated per container (e.g., application 108 ₃ running fromcontainer 116 ₁), one of ordinary skill in the art can appreciate that,in some implementations, multiple applications may be run from eachcontainer. For example, in container implementations using Docker, onlyone application per container may be implemented, while containerapplications using Linux containers or LXC, a plurality of applicationsmay run from each container.

FIG. 1C illustrates an example container on bare metal. As an option,one or more variations of example container or any aspect thereof may beimplemented in the context of the architecture and functionality of theembodiments described herein. The example container or any aspectthereof may be implemented in any environment.

The embodiment shown in FIG. 1C is merely one example. As shown, thebare metal architecture 112 comprises one or more containers (e.g.,container 116 ₃ and container 116 ₄) each of which comprise a selectionof operating system modules that run on the hardware 101 ₃.

Containers deployed in such an architecture can be extremelylightweight, possibly involving a pod technology that federates commoncode blocks so only one copy of the module is needed even when multiplecontainers uses the same code block. This architecture as shown is voidof support for ongoing management of the deployed containers.

FIG. 1D1 and FIG. 1D2 depict block diagrams of a container supportsystem 1D00 used for configuring, deploying, and managing containers ina virtualization environment. As an option, one or more variations ofcontainer support system 1D00 or any aspect thereof may be implementedin the context of the architecture and functionality of the embodimentsdescribed herein. The container support system 1D00 or any variation oraspect thereof may be implemented in any environment.

High-Level Components

As shown a control virtual machine 130 ₁ (CVM) includes a user interface131 (UI) that provides a man-machine interface that can comprise agraphical user interface and/or a GUI API as well as a command linestyle interface with a CLI API. Either or both of the interfaces can beemployed by a user to schedule or carry out a set of user operations.More particularly, the user interface 131 permits a user to interactwith various modules of the container support system so as to configure,deploy, and publish containers in a hyper-converged environment. Avirtualized controller (e.g., control virtual machine 130 ₁) includescomponents that can communicate with components of a container servicevirtual machine (e.g., container service machine 150). In someembodiments and as shown, a control virtual machine 130 ₁ communicateswith a container service machine 150 (CSM) over one or more links 114.Such communication can be facilitated by a services module 140 and acontainer agent 160. A container service virtual machine runs on top ofa hypervisor and hosts a user container to provide services (e.g.,storage I/O (input/output or IO) services) to the user container. Inmany cases a user container is preconfigured (e.g., within a Dockerrepository) with file system components that are intended for use with aparticular (e.g., CIFS, NFS, other standard) file system. However in thecontext of a hyper-converged clustered environment where both localstorage (e.g., node-local storage) and networked storage devices (e.g.,shared remote storage) are combined into a storage pool (e.g., storagefacility 162), the additional capabilities of a control virtual machineare needed.

Returning to the discussion of the UI, the nature and content of theinteractions and communications depend at least in part on the intent ofthe user as indicated by the user's submission of user operations viathe UI. Strictly as examples, the foregoing components operate incoordination so as to facilitate container configuration and managementoperations such as “create container”, “start” a container, “stop” acontainer, and “pause” a container. Other examples might involveconfiguration and management of the environment in which the containersoperate. As an example, the foregoing components operate in coordinationso as to facilitate storage pool management, volume management, as wellas to facilitate capture and reporting of statistics, etc. Any componentor components within the container support system might be tasked orpartitioned so as to participate in configuration of the containerservice machine and/or the containers that run within the containerservice machine. As can be observed, when a user container (e.g., UC₁,UC₂, . . . , UC_(N)) runs within a container service machine, it canaccess facilities beyond the bare metal. More particularly, containersthat run within a container service machine have access to all of theservices available to a user virtual machine, plus additional servicesas may be provided by a hypervisor (e.g., hypervisor 104 ₂) and/or anunderlying operating system. The operating system underlying thecontainer service machine 150 might be different from the operatingsystem or operating system components that might be included in a usercontainer (e.g., UC₁, UC₂, . . . , UC_(N)).

In some cases, a container service machine 150 might include a volumemanager interface 154 and/or any number of service interfaces (e.g.,service interface 155 ₁, . . . , service interface 155 _(N)), whichservice interfaces might include access to services pertaining to anetwork manager or other service interfaces. Such interfaces providesystem functions (e.g., configuration and I/O) to user containers thataccess cluster facilities (e.g., storage facilities, and/or loadbalancing facilities and/or network facilities or other clusterfacilities). A volume manager interface 154 and/or the serviceinterfaces can be separately implemented, or can be implemented in onemodule, or can be subsumed by another module within the containerservice machine 150. A network manager can provide networking servicesthat serve to “harden” the container service machine against maliciousactivities, and/or that serve to protect the container service machinefrom accessing container repositories that are known or become known tocontain malicious code.

In some cases, and as shown in FIG. 1D1, a container service machine 150might run in a one-to-one deployment (e.g., one-container servicemachine to a node). In other cases, and as is shown in FIG. 1D2, a firstcontainer service machine might run on node N1, and a second containerservice machine might run on node N2, and so on for up to N nodes. In acluster setting one of the container service machines might bedesignated as a cluster master container service machine. Functionspertaining to a cluster master container service machine are discussedhereunder.

Returning to the discussion of the shown control virtual machine 130 ₁,in addition to the aforementioned configuration and control functionspertaining to user containers, the control virtual machine 130 ₁includes functionality to populate one or more container servicemachines with preconfigured executable containers 165 that are retrievedfrom a container repository and registry 164. A set of user containersmight be selected, and downloaded, and configured individually andcollectively into an application group 151. The set of user containersin application group 151 can be configured individually and/orcollectively so as to function as a group, possibly to carry out aserializable series of operations (e.g., as a pipeline of operations),and/or to carry out a series of parallelizable or partiallyparallelizable operations (e.g., a fork-join operation). Theaforementioned container agent can perform configuration and otheroperations autonomously, or in conjunction with the control virtualmachine.

More particularly, the control virtual machine 130 ₁, and/or thecontainer service machine 150 can facilitate downloading of containersfrom a container repository and registry 164. Configuration of a set ofcontainers might involve (1) parameterization and/or instantiation of acontainer into a CSM, (2) managing some or all of a set of containers asa swarm, (3) deployment of containers onto specific nodes, and/or (4)invocation of a set of containers, possibly in a particular sequence,and possibly involving election of a leader from among the set. As such,a control virtual machine in this environment might include modules inthe form of a composer module (e.g., to perform parameterization and/orinstantiation of a container into a CSM, possibly including deploying aset of containers working together as an application), a swarm manager136 (e.g., to subsume and manage some or all of a set of containers as aswarm), a deployer module 138 (e.g., to map containers onto specificnodes), and an execution module 137 (to invoke a container according toa defined invocation regime).

Any or all of the aforementioned modules can be partitioned into acontainer service module 134. Any functions needed by the containersbeing hosted in the container service machine can be availed by aseparate instance of leadership module 143 and/or a separate instance ofservice module 140, which modules can also serve to facilitatecommunication (e.g., over a link such as link 114) between any modulesof the control virtual machine 130 ₁ and any modules of the containerservice machine 150. The link and its endpoints can be operating systemand hypervisor agnostic. In the example shown, the operating system 102₃ as well as its corresponding hypervisor 104 ₃ can be different fromthe operating system 102 _(M) and its corresponding instantiation ofhypervisor 104 _(M).

In some cases, a particular container conforms to a particular set ofrules or types. A type might be characterized by one or more “kinds”,and a kind might correspond to a respective set of configurationparameters and/or configuration sequences. Any one or more distinct setsof configuration parameters and/or configuration sequences can becodified into a kind plugin 133, which plugin facilitates configurationof any instances of a particular type of container. Strictly as oneexample, a particular kind plugin might be used to configure a localarea network or wide area network that is present or accessible in theenvironment. A kind plugin is merely one from among a large set ofentities that can be accessed from an entities repository 139, which inturn can be accessed and configured (e.g., by a container kindconfigurator) for use by any container. One example of and use for anentity might include a specific configuration description (e.g., atemplate) that can be used in turn to characterize aspects of anenvironment under which a subject container might run. Differentapplication can be associated with different templates that suit aparticular deployment, such as might pertain to an a priori knownapplication (e.g., a compute-intensive application, or amemory-intensive application, etc.). In some cases, such templates arelabeled and exposed as pertaining to a “small” configuration or a“large” configuration. The configuration can be specific to an a prioriknown application, and can be specific regarding partitioning and/ormapping to the cluster resources. For example, a configuration canspecify a rule or grammar of the form “<operand><operator><operand>”,such as “<operand=application_name><uses><operand=configuration_name>”,or “<operand=application_name><uses><operand=API_name>”, or such as“<operand=application_name><uses><operand=configuration_name>”, or suchas“<operand=application_name><deploys onto><operand=Node_ID>”. Theforegoing are merely examples; other rule formats and/or grammars and/oroperands and/or operators are envisioned. Another example of and use foran entity might include a file layout or a vDisk specification that canbe used by a container.

A CSM (e.g., container service machine 150) might be preconfigurable forsome specific purpose or purposes. For example, a CSM can bepreconfigured with to run with specific access privileges and/orpreconfigured to run with a particular set of hardware resources orquotas, or with any configurable or parameterizable characteristic.

User Interfaces

Strictly as examples, the user interface 131 can employ a GUI and/or aCLI to perform the following operations:

-   -   Any forms of create, replace, update, or delete operations        (CRUD) operations for a named container service machine.    -   CRUD operations for creating a named pool of container service        machines (see FIG. 1D2).    -   Deploying a named container on a named container service machine        or within a named pool of container service machines.    -   Stop/Start/Pause/Remove operations on a container using a        container ID.    -   Operations to create container volumes in persistent storage.    -   An operation to collect and report statistics pertaining to a        specific container or pertaining to a particular container        service machine, or from one or more container machine pools.    -   Operations to specify one or more container registries and/or        container repositories (e.g., to “docker hub”).

Any of the above operations can be entered via a GUI or via a CLI, orboth. In some cases, certain operations (e.g., create a dockercontainer) can be performed using a “docker CLI”. Moreover, a GUI or aCLI, or both can be configured to allow an authorized user to run thedocker CLI remotely on a specific container machine. In some cases a setof private/public key pairs are used for authentication and/orauthorization.

Container Service Module in the Control Virtual Machine

An instance of a control virtual machine 130 ₁ runs on each node. Asshown, the control virtual machine 130 ₁ comprises several modules thatare dedicated to managing containers. One such module is depicted as thecontainer service module.

The functions of this module include functions of (1) a swarm manager;(2) operations to access “hub.docker.com” and other containercommunities; (3) a master container service, which in turn facilitatesdefinitions for the container kind configurator 132; (4) creatingdetails of the containers in the entity repository 139; (5)instantiating a container within one or more of the container servicemachines, and so on.

In one scenario, a user simply indicates their intent to deploy aparticular container. The decision as to which particular containerservice machine in the container service machine pool container is to bedeployed to is performed by the container service module 134, possiblyin conjunction with internal modules (e.g., the swarm manager) and/orexternal modules (e.g., the shown services module 140). In addition tothe aforementioned functions, the services module 140 facilitatesnetwork configuration, volume management, and lifecycle management ofany container service machine. Additionally instances of a containerservice machine 150 can register a container with a leadership module143 so as to bring the container into a group for leadership election.

Communications between the control virtual machine 130 ₁ and thecontainer service machine 150 can occur over the shown link 114. In manycases, communication into and out of the container service machine 150can be performed by the shown container agent 160. The link can beimplemented using any known communication techniques or modes. Strictlyas an example, such a link can rely on inter-process communications(IPC), data message passing through shared memory, IP protocols,tunnels, etc.

Persistent Storage Facilities for Containers

Certain container architectures do not natively support persistentstorage. Given this architecture, if a container is moved from onelocation (e.g., node) to another location (e.g., another node) afacility needs to move its storage with it. Various types of plugins(e.g., volume plugin 135) can be stored in, and retrieved from, theentities repository 139. Such volume plugins provide containerdeployments to be integrated with various persistent storage systems.Such integration using volume plugins support data volumes that persistbeyond the lifetime of a single container and/or its container servicemachine host. Some containers support use of user defined volume namesfor associating container data with some external persistent storagevolume. Such a persistent storage facility results in a statefulcontainer that can be moved from one server to another while retainingat least portions of its state.

In some cases, a volume plugin 135 interacts with and/or is implementedby a daemon 157 that resides on the container service machine. Variousdaemon functions can be facilitated by and/or be included within thecontainer agent 160, or elsewhere. A daemon can have a strong or weakaffinity with an application group 151 and/or with any user container.Such a daemon can create named mount points for external volumes basedon instructions from a container that has an affinity to the particularinstance of a daemon 157. In some cases the aforementioned volume pluginreceives a callback whenever a named volume is created. Further, thedaemon can handle mounting and unmounting of a volume or volume groupfrom a container.

In one scenario, the daemon calls into the volume plugin when a volumeis to be mounted or unmounted. The volume plugin forwards the mount orunmount request to the container agent 160 which will attach the volumeor volume group to the parent VM. The daemon can also initiate and/orperform steps pertaining to deleting the named volume.

FIG. 1D3 depicts a block diagrams of a container support system 1D00where portions of the virtualized controller are implemented in adistributed fashion. As shown, some functions within the distributedcontainer service module 142 ₁ can be implemented within a VM and somefunctions within the distributed container service module 142 ₁ can beimplemented within a container. Any functions can be distributed acrosseither the VM or the container (e.g., storage functions to be performedover or by the storage devices within the storage facility 162). Theshown embodiment depicts the situation where the swarm manager 136 (seeswarm manager within the containerized distributed container servicemodule 142 ₂) that was formerly a module within the VM (see dotted linemodule). The relocated swarm manager 136 can fulfill all of thefunctions of a swarm manager even when the swarm manager is operatingwithin the containerized distributed container service module 142 ₂.

In some cases, such as is depicted in FIG. 1D4, any virtualizedcontainer can comprise a distributed container service module (e.g.,distributed container service module 142 ₃ and distributed containerservice module 142 ₄) which can be implemented in master/slaverelationships. More particularly, any virtualized controller can bedesignated as a MASTER, and any other virtualized controller can bedesignated as a SLAVE. In some cases there may be multiple instances ofvirtualized controllers that are designated as a SLAVE (e.g., SLAVE1 andSLAVE2, as shown). A SLAVE can switch over to serve as a MASTER if sodetermined. In a situation where a MASTER fails (as depicted in FIG.1D5), a SLAVE might detect the loss of the MASTER, and might pick-upMASTER responsibilities. Such a transition is depicted in FIG. 1D5,where a former SLAVE (e.g., SLAVE1 of FIG. 1D4) automatically picks-upthe responsibilities of the former MASTER (e.g., the MASTER of FIG.1D4).

The modules as shown and discussed in the foregoing combine tofacilitate setup, deployment, and publishing of containers within avirtualization environment. Further, as discussed in the followingfigures FIG. 1E, FIG. 1F, and FIG. 1G, the herein disclosed techniquesserve to establish a container-centric environment that supportsconfiguration and invocation of groups of containers.

FIG. 1E presents a flowchart of an environment preparation technique1E00 as used by administrators (e.g., system admins or cluster admins)in systems for configuring, deploying, and managing containers in avirtualization environment. As an option, one or more variations ofenvironment preparation technique 1E00 or any aspect thereof may beimplemented in the context of the architecture and functionality of theembodiments described herein.

The embodiment of FIG. 1E is merely one example for configuring anenvironment. As shown, an administrator accesses a UI (e.g., userinterface 131) to establish a set of privileges (step 172). Theprivileges can be assigned to any aspect of actions to be taken, whetherby a user or by a virtual machine or by a container. The actions takencan span the entire scope of operations performed on nodes (e.g.,networking configurations), operations performed within clusters (e.g.,storage configuration), and/or operations performed that relate toaspects of inter-cluster operation and/or cluster-to-external facilityoperation (e.g., security operations).

Specifically, privileges can be established that pertain to safe accessto external repositories of containers (e.g., a docker site). When asafe access technique and corresponding privileges are established andenforceable (e.g., possibly by restricting access to external sites onlythrough a hardened instance of a container service machine) theadministrator can configure (and make available to users) a retrievalcapability to access external container registries and containerrepositories 174. In some cases, the retrieval capability includesdownloading through hardened ports. Accordingly at step 176, theadministrator configures WAN and/or LAN ports, possibly throughconfiguration of a router and/or configuration of VLANs. Additionally,the environment preparation technique 1E00 can include configuringstorage areas, including specific locations and/or devices in thestorage pool (step 178). As one specific case, using the environmentpreparation technique 1E00 or any aspect thereof an administrator canspecify which storage areas can be used to create volume groups (e.g.,to establish volumes to be used as persistent storage for usercontainers).

In some cases, certain external repositories of containers areconfigured as whitelisted or preferred sites, and others might beblacklisted or blocked or otherwise restricted from access, while stillothers might be only partially restricted. In some cases specificdownloads identified by a filename or file checksum are restricted.

The environment so established, either by default values or resultingfrom acts taken during environment preparation, serves for ease ofprogression through a workflow as shown and discussed as pertaining toFIG. 1F.

FIG. 1F presents a flowchart of a multi-phase workflow 1F00 as used byadministrators and developers in systems for configuring, deploying, andmanaging containers in a virtualization environment. As an option, oneor more variations of multi-phase workflow 1F00 or any aspect thereofmay be implemented in the context of the architecture and functionalityof the embodiments described herein. The multi-phase workflow 1F00 orany aspect thereof may be implemented in any environment.

The embodiment shown in FIG. 1F is merely one example. The shownworkflow includes a setup phase 181, a development phase 183, and apublishing phase 187. In the setup phase, an administrator or privilegeduser downloads a driver and/or toolkit from a preconfigured location(step 180). The downloaded driver and/or components in the toolkit aresufficient to create an instance of a container service machine (step182) within the environment established prior to, or in conjunctionwith, the performance of environment preparation technique 1E00.Operations available during creation of an instance of a containerservice machine include specification of sizing parameters, includingquotas or limits pertaining to node or cluster resources (e.g., CPUusage limits, memory usage limits, disk size limits, etc.).

Concurrently or sequentially, a developer can avail of the environmentand/or container service machine as established during the setup phase.Specifically, a developer can develop a container for a specificfunction (step 184), possibly writing container code from scratch, orpossibly using any containers that were made available through thecontainer registry and container repository. At some moment in time thedeveloper will commit code to a code repository (step 185), and performtests (decision 186) using the committed code. The various activities inthe development phase may be repeatedly performed in a loop and, asshown, until such time as the developer deems that the tests pass. Insome cases, the tests performed include connecting to the aforementionedinstance of container service machine (step 182), which in turn providesa preconfigured environment in which the developer can test thenewly-developed container in an in situ setting.

The container can be published for use by others. Specifically, thedeveloper or administrator can push the newly-developed container to arepository (step 188) and update the corresponding registry (step 189).In some cases, a user or administrator might want to remove and/orderegister a previously published container. Such a facility is providedvia the user interface 131.

In some cases a developer may partition an application into manyinterrelated containers. A group of interrelated containers can beidentified as an application group. Such a group can be managed byfacilities provided by the control virtual machine 130 ₁ and/or thecontainer service machine 150. Specifically, mapping of an instance of acontainer to a particular node and/or to a particular container servicemachine can be performed with or without user intervention. One flow forcontainer-to-node mapping is shown and described in FIG. 1G.

FIG. 1G presents a flowchart of a container-to-node mapping technique1G00 as used in systems for configuring, deploying, and managingcontainers in a virtualization environment. As an option, one or morevariations of container-to-node mapping technique 1G00 or any aspectthereof may be implemented in the context of the architecture andfunctionality of the embodiments described herein. The container-to-nodemapping technique 1G00 or any aspect thereof may be implemented in anyenvironment.

A user might want to map a container or group of containers to a node orgroup of nodes (step 192). In some cases, a user might prepare a map apriori, such as in cases where the user is self-managing nodeallocations. In other cases, a user might want to merely identify acontainer or group of containers as belonging to an application group,and then allow the container service machine or other facility toperform the mapping. In the latter case, a user might consult acontainer service module to identify prospective mapping of containersto nodes (step 194). The user can then accept a mapping, or can modify amapping (step 196). Upon acceptance of the modified or unmodifiedmapping, the user can invoke the container or application group (step198).

The foregoing configuration examples are merely some examples. Manyvariations for deployment of containers or groups of containers, whetherhosted within a container service machine or whether hosted on baremetal, are possible within the scope of systems that are configuredusing the aforementioned techniques. Moreover, the herein-disclosedarchitecture for managing I/O and storage for a virtualizationenvironment using executable containers and virtual machines can beflexibly mapped onto a wide variety of hardware configurations,including onto a small number of nodes (e.g., one node), or onto anarray of many nodes, or onto a fully-configured cluster comprising manynodes and a storage pool, or onto multi-cluster platforms, etc. Further,various use models are supported by various respective partitioning ofcomputing resources and storage facilities.

-   -   FIG. 1H and FIG. 1I present a flowcharts of storage pool use        models. The flow 1H00 commences upon initialization of a control        virtual machine to expose a storage pool to computing resources        (step 1H10). A user might retrieve an executable container from        a container repository (step 1H30) and use ancillary functions        (e.g., API calls) to register the retrieved executable container        with the control virtual machine (step 1H40). The control        virtual machine then invokes the executable container (step        1H50). The executable container might need to define and/or        access persistent storage, at which time the control virtual        machine receives storage access I/O commands issued from the        executable container (step 1H60). Additional storage access I/O        commands can be issued from the executable container, which        cause the control virtual machine to process the additional        storage access I/O commands (step 1H80). Processing of storage        I/O commands by the control virtual machine can include        initiation of actions that are performed by, or for, or within        the storage devices of the storage pool.

Flow 1I00 depicts a use model that includes a container service machine.As shown, the flow commences upon initialize a control virtual machineto expose a storage pool (step 1I10). Another step initializes acontainer service machine to access the storage pool through the controlvirtual machine (step 1I20). A user or administrator might take actionsto retrieve an executable container from a container repository (step1I30), which executable container is used to populate the retrievedexecutable container into the container service machine (step 1I40). Thecontainer service machine invokes the executable container (step 1I50).The executable container raises storage I/O commands which are in turnreceived by the container service machine (step 1I60). In some cases,the storage access I/O commands issued from the executable container arereceived and responded to by the container service machine (step 1I60).In other cases, the storage access I/O commands issued from theexecutable container are forwarded by the container service machine to acontrol virtual machine (step 1I70). In such cases, the control virtualmachine responds to the storage access I/O commands by performingoperations in accordance with the storage access I/O commands and/orforwarding modified or unmodified storage access I/O commands so as tocause initiation of actions that are performed by, or for, or within thestorage devices of the storage pool (step 1I80). The aforementionedsteps of FIG. 1H and FIG. 1I are merely examples, and other flows andpartitions are possible so as to accommodate various computing loadsand/or reliability factors such as are found highly concurrent computingscenarios and/or in highly resilient configurations.

In particular, the partitions of FIG. 1D3, FIG. 1D4, and FIG. 1D5 depicthow virtualized controller functions can be freely partitioned or movedbetween virtual machine implementations and containerizedimplementations. As shown, the distributed container service module 142₂ comprises a swarm manager 136. Virtualized controller functions (e.g.,the shown swarm manager) can be implemented within any variations of avirtualized controller (e.g., implemented as or within a virtual machineor implemented as or within a container). The example of a swarmcontroller is merely one example of functions that can be freelypartitioned. Any functions or groups of functions can be freelypartitioned or moved between a virtual machine implementation and acontainerized implementation so as to facilitate inter-functioncommunication (e.g., to reduce I/O over the links and instead rely onintra-process communication such as subroutine calls).

Merely as an example partitioning of services between container servicemachine and a control virtual machine, FIG. 3 depicts a single-nodeconfiguration 300. As an option, one or more variations of single-nodeconfiguration 300 or any aspect thereof may be implemented in thecontext of the architecture and functionality of the embodimentsdescribed herein. The single-node configuration 300 or any aspectthereof may be implemented in any environment.

More specifically, FIG. 3 illustrates an example architecture of a nodeconfiguration 300 implementing a container service machine 150 and acontrol virtual machine 130 ₄. Additionally, node configuration 300comprises an operating system 102 ₇, with a hypervisor 104 ₆. In thisembodiment the container service machine 150 includes an operatingsystem, such as Linux, that supports container technologies. Asillustrated, the container service machine has a root directory 307,which corresponds to the container service machine's instance of a rootfile system 308. Further, the container service machine 150 comprisestwo example containers, a MySQL container 310, which runs a MySQLserver, and a retail website container 312, which runs an example retailwebsite.

Each container runs as a virtualized computer in that each containercomprises an isolated file system, a process environment with its ownprocesses, and an IP address. A container's file system may comprise abase image (e.g., Ubuntu), and may layer on additional images andapplication execution layers (e.g., MySQL, web services), as necessary.In some implementations, the multiple layers that make up a givencontainer appear as single file system using a union mount process.Using union mounts, changes to a read-only layer may be completed usinga copy-on-write operation, where the file to be modified in theread-only layer is copied to an execution space where the changes aremade to the copied file.

As mentioned, a container service machine can implement containers as aforms of isolated file systems. As such, applications running fromwithin one container do not “see” other containers as siblingdirectories in the root file system 308. Instead, applications runningin a container only see and work with their own containerized filesystems, which appear to the applications as “true root” directoriesthough they are not. Thus, containers provide security measures againstmalicious activities by isolating applications within a containerexecution environment while still allowing containerized applications tobe installed and run with low system requirements.

An additional advantage of the node configuration 300 is that eachcontainer is running within a container service machine, which providesan additional robust layer of network security. For example, if amalicious web user compromises the retail website container 312 to gainadmin access to the root file system 308, the malicious user is stilltrapped within the retail website container service machine. As such,the malicious user has not gained access to the node's operating system.

In some embodiments, containers running applications of differentsensitivity levels (e.g., different admin policies or service levelagreements (SLAs)) may be placed in different container service machinesfor further isolation. For example, if a malicious web user compromisesthe retail website container 312 and gains access to the root filesystem 308, the malicious web user might then be able use that access tocompromise the MySQL container 310 (which may contain credit cardinformation, etc., belonging to retail website customers) or any othercontainers running on top of the root file system 308. Instead,sensitive containers (e.g., containers running applications withsensitive information) may be placed on a separate container servicemachine, such as isolated VMs 320. As such, if the retail websitecontainer 312 is breached, the malicious user has not gained access toapplications or information in the isolated VMs 320.

In some embodiments, containers on the container service machine such asa My SQL server with non-sensitive information may interface with theisolated VMs 320 through a container interface module 322, which may runas a web application that uses TCP/IP protocol to retrieve or storesensitive information in the isolated VMs 320 (e.g., using tokens,keys). One of ordinary skill in the art can appreciate that thecontainer interface module 322 may be run directly on the root filesystem 308 as an application of the container service machine, or it mayrun as an application in any other container.

Further, container interface module aspects may be implemented as alayer within any of the containers running on the container servicemachine 150. For example, the MySQL container 310 may be modified withan additional layer or application with specialized interfaceinstructions, such that when sensitive information is queried (e.g.,created, modified, updated, or deleted) by the MySQL application, thecontainer interface module layer is invoked to send the query to anisolated VM 320, which may then store it in its isolated environment.Further, one of ordinary skill in the art appreciates that the isolatedVM 320 may comprise containerized applications or run applicationsdirectly on its VM operating system.

FIG. 3 also illustrates a control virtual machine 130 ₄ running abovethe hypervisor 104 ₆. As explained above, the control virtual machinemay act as the storage controller for the node configuration 300. Assuch, although a container running in the container service machineappears as a logical directory with files (e.g., the folders/directoriesinside retail website container 312), the creation and/or modificationof that container's directory corresponds to I/O operations that occurthrough the container service machine, which writes to its vDisk 170through the control virtual machine 130 ₄.

For example, if an application running in the retail website container312 stores data, the application may create a directory within thecontainer and store the data inside the newly created directory.However, the actual I/O operations occur through the operating system onthe container service machine. The operating system on the containerservice machine writes to its exposed vDisk (e.g., as exposed by thecontrol virtual machine 130 ₄), which further corresponds to an iSCSIrequest that is directed to the control VM to be handled in adistributed manner (e.g., using control virtual machine administrativemodules 314 ₁), as explained in further detail below.

FIG. 4 illustrates a one-container-service-machine-per-node architecture400 as used in systems that support cluster-wide configuration ofcontainers in a virtualization environment. As an option, one or morevariations of one-container-service-machine-per-node architecture 400 orany aspect thereof may be implemented in the context of the architectureand functionality of the embodiments described herein. Theone-container-service-machine-per-node architecture 400 or any aspectthereof may be implemented in any environment.

FIG. 4 illustrates an alternative container-within-containerarchitecture that can be used to implement a virtualized computerstorage environment, according to some embodiments. In FIG. 4, each node(e.g., node 202 ₃ and node 202 ₄) implements a respective instance ofservice container 404 ₁ and service container 404 ₂ (e.g., each beinginstances of a container service machine 150). The service container 404₁ and service container 404 ₂ may be implemented as distributed storagecontrollers for the shown user containers using a routing table asdiscussed infra. The nodes of FIG. 4 might have an operating system(e.g., operating system 102 ₈, operating system 102 ₉). In some cases,the containers might have sufficient operating system resources suchthat an operating system image is not needed in thiscontainer-within-container architecture.

FIG. 5 illustrates a one-control-virtual-machine-per-node architecture500 as used in systems that support cluster-wide configuration ofcontainers in a virtualization environment. As an option, one or morevariations of one-control-virtual-machine-per-node architecture 500 orany aspect thereof may be implemented in the context of the architectureand functionality of the embodiments described herein. Theone-control-virtual-machine-per-node architecture 500 or any aspectthereof may be implemented in any environment.

FIG. 5 illustrates an alternative architecture that may be used toimplement a virtualized computer storage environment, according to someembodiments. There, each node (e.g., node 202 ₅ and node 202 ₆)implements user containers directly on the nodes' operating system.Further, the service virtualized machines are implemented as controlvirtual machine 130 ₅ and control virtual machine 130 ₆, respectively,above the hypervisors. The nodes of FIG. 5 include an operating system(e.g., operating system 102 ₁₀, operating system 102 ₁₁) that comportswith respective hypervisors (e.g., hypervisor 104 ₇ and hypervisor 104₈).

The shown embodiment includes a plurality of nodes (e.g., 202 ₅ and node202 ₆) wherein each node of the plurality of nodes includes a controlvirtual machine that is configured to operate as a storage controllerdedicated to the node (e.g., control virtual machine 130 ₅ and controlvirtual machine 130 ₆) as well as one or more user containers per node(e.g., user container 252 ₅₁, user container 252 ₅₂, user container 252₅₃, user container 252 ₆₁, user container 252 ₆₂, and user container 252₆₃). The shown plurality of storage devices in the storage pool 242 areaccessed by the one or more user containers via storage access I/Ocommands (e.g., vDisk I/O) through a corresponding node-specific controlvirtual machine. The node-specific control virtual machines are eachconfigured to manage and/or facilitate access by the user containers tothe plurality of storage devices. Use of vDisks (as shown) is merely oneembodiment and other storage I/O can be initiated by a user container,then delivered to a respective node-specific control virtual machine,which node-specific control virtual machine in turn carries out storageI/O to and from the storage devices. Strictly as one example, if acontainer requests file system operations such as creating a directoryand then issues requests to store a file in that directory, the filesystem operations are at first initiated by the user container, thenreceived by the node-specific control virtual machine. In some cases thecontainer-initiated file system operations are reformatted before beingperformed by the node-specific control virtual machine. For example, theactual I/O operations to be performed on storage devices in the storagepool are formed by the node-specific control virtual machine as I/Orequests and delivered to the storage device pertaining to the file.

FIG. 6 illustrates a foreign OS architecture 600 as used for runningcontainers on top of a foreign OS in systems that support cluster-wideconfiguration of containers in a virtualization environment. As anoption, one or more variations of foreign OS architecture 600 or anyaspect thereof may be implemented in the context of the architecture andfunctionality of the embodiments described herein. The foreign OSarchitecture 600 or any aspect thereof may be implemented in anyenvironment.

FIG. 6 illustrates an alternative architecture that may be used toimplement a virtualized computer storage environment, according to someembodiments. There, each node (e.g., node 202 ₇ and node 202 ₈) runs ahypervisor (e.g., hypervisor 104 ₉ and hypervisor 104 ₁₀) on itsrespective operating system (e.g., operating system 102 ₁₂, operatingsystem 102 ₁₃). Above the hypervisors, virtual machines (e.g., virtualmachine 601 ₁₁, virtual machine 601 ₁₂, . . . , virtual machine 601_(1N); virtual machine 601 ₂₁, virtual machine 601 ₂₂, . . . , virtualmachine 601 _(2N)) are instantiated. Any of those virtual machines runcombinations of user containers (e.g., user container 252 ₁₁, usercontainer 252 ₁₂, user container 252 ₁₃, user container 252 ₂₁, usercontainer 252 ₂₂, and user container 252 ₂₃) as well as a respectiveservice container (e.g., service container 610 ₁ and service container6102).

FIG. 7A, FIG. 7B1, FIG. 7B2, FIG. 7B3, and FIG. 7C illustrate variousinter-node communication techniques as used in systems that supportconfiguring, deploying, and managing containers in a virtualizationenvironment. As an option, one or more variations of inter-nodecommunication techniques or any aspect thereof may be implemented in thecontext of the architecture and functionality of the embodimentsdescribed herein. The inter-node communication techniques or any aspectthereof may be implemented in any environment.

FIG. 7A illustrates an example approach that can be taken in someembodiments to submit I/O requests to the control VMs (e.g., controlvirtual machine 130 ₇ and control virtual machine 130 ₈) as receivedfrom a user VM, or from a subsumed user container. For example, in thisapproach, two node configurations are depicted, namely node 202 ₉ andnode 202 ₁₀. The user container virtual machine 250 ₁ comprising one ormore user containers sends I/O requests 750 ₁ to the control VMs in theform of iSCSI or NFS requests. The I/O request may correspond to a filesystem action within any of the aforementioned containers. For example,if a container performs file system operations such as creating adirectory within its user virtual machine and stores a file in thedirectory, the file system operations are performed on the vDisk forthat VM. However, the actual I/O operations are formed as I/O requestsand handled by the control virtual machine.

The term “iSCSI” or “Internet small computer system interface” refers toan IP-based storage networking standard for linking data storagefacilities together. By carrying SCSI commands over IP networks, iSCSIcan be used to facilitate data transfers over intranets and to managestorage over any suitable type of network or the Internet. The iSCSIprotocol allows iSCSI initiators to send SCSI commands to iSCSI targetsat remote locations over a network. In another embodiment, the containerservice machine sends I/O requests 750 ₁ to the control VMs in the formof NFS requests. The term “NFS” or “network file system” interfacerefers to an IP-based file access standard in which NFS clients sendfile-based requests to NFS servers via a proxy folder (directory) called“mount point”. Going forward, this disclosure will interchangeably usethe term iSCSI and NFS to refer to the IP-based protocol used tocommunicate between the hypervisor and the control VM. Note that whileboth protocols are network-based, the currently described architecturemakes it possible to use them over the virtual network within thehypervisor. No iSCSI or NFS packets will need to leave the machine,because the communication—the request and the response—begins and endswithin the single hypervisor host.

The container service machine structures its I/O requests 750 ₁ into theiSCSI format. The iSCSI or NFS request designates the IP address for acontrol VM from which the user desires I/O services. The iSCSI or NFSI/O request is sent from the container service machine to a virtualswitch 702 ₁ within hypervisor 104 ₁₁ to be routed to the correctdestination. If the request is intended to be handled by the control VMwithin the same server, then the iSCSI or NFS request is internallyrouted within that server to the control virtual machine 130 ₇. Asdescribed in more detail below, the control virtual machine 130 ₇includes structures and/or modules, such as the aforementioned controlvirtual machine administrative modules 314 ₁ (see FIG. 3) to properlyinterpret and process the I/O requests 750 ₁.

It is also possible that the iSCSI or NFS request will be handled by acontrol VM on another server. In this situation, the iSCSI or NFSrequest will be sent by the virtual switch 702 ₁ to a real physicalswitch to be sent across the network 240 to the other server. Thevirtual switch 702 ₂ within hypervisor 104 ₁₂ will then route therequest to the control virtual machine 130 ₈ for further processing.

In some embodiments, the I/O requests 750 ₁ from the user containervirtual machine 250 ₁ is a part of a SCSI protocol request to a storagedevice. The hypervisor may convert the SCSI request into an iSCSI or anNFS request as part of its hardware emulation layer. In other words, thevirtual SCSI disk attached to the user VM is either an iSCSI LUN or anNFS file in an NFS server. In this approach, an iSCSI initiator or theNFS client 806 software may be implemented within the hypervisor toconvert the SCSI-formatted requests into the appropriate iSCSI- orNFS-formatted requests that can be handled by the control virtualmachine 130 ₈.

According to some embodiments, a control VM runs the Linux operatingsystem. As noted above, since the control VM exports a block device orfile access interface to the user VMs, the interaction between thecontainer service machines and the control VMs follows the iSCSI or NFSprotocol, either directly or indirectly via the hypervisor's hardwareemulation layer.

FIG. 7B1 illustrates an approach for implementing user containers (e.g.,user container instance 252) in conjunction with container servicemachines (e.g., container service machine 150 ₁, container servicemachine 150 ₂). In this embodiment, I/O requests 750 ₂ are directed tothe OS of node 202 ₁₁. For instance, the I/O request is directed to avirtual router (i.e., virtual router 752 ₁, virtual router 752 ₂) thatdirects the I/O request to the container service machine for that node(e.g., container service machine 150 ₁, container service machine 150₂). In some embodiments, the virtual router 752 ₁ corresponds to a mountpoint, such as a LUN that corresponds to a storage volume. The OS isconfigured to create all containers on a storage device that is mappedto the mount point or LUN. In some embodiments, the I/O requests 750 ₂may be directed to the storage volume mapped to the mount point or LUNby writing or reading data from that storage volume. The containerservice machines 150 ₁ may operate on data in the storage volume andmove it to the distributed storage pool over network 240. Data in thestorage pool can be read by other nodes such as node 202 ₁₂. In someembodiments, the OS may directly implement a virtual switch (e.g., theaforementioned virtual switch 702 ₁, virtual switch 702 ₂) of FIG. 7A.In some embodiments, the user container instance 252 can directly mountor direct iSCSI requests 788 directly to the container service machine150 ₁.

In some node implementations, such as is shown as node 202 ₁₂, a virtualrouter 752 ₂ may be part of a modified operating system that handles allcontainer I/O operations by forwarding them to the container servicemachine 150 ₂ using a routing table or other configured parameter.

FIG. 7B2 illustrates an approach for implementing user containers (e.g.,user container instance 252) in conjunction with container servicemachines (e.g., container service machine 150 ₁, container servicemachine 150 ₂). In this embodiment, I/O requests 750 ₂ are written to,and read from, a shared memory facility that is accessible for READ andWRITE by two or more different nodes.

The nodes are each configured to manage and/or facilitate access by auser process (e.g., a user container or a user container within a usercontainer virtual machine) to a plurality of storage devices. StorageI/O commands can be communicated (e.g., read and/or written) betweennodes using an arrangement of message passing and/or mailboxes, and/orlocks, and or semaphores implemented using the shared memory facility.Use of iSCSI (e.g., iSCSI requests 788) is merely one embodiment andother storage I/O can be initiated or carried out in accordance with anystorage device protocol or command set.

The shared memory facility serves to implement a delivery mechanism suchthat a target node (e.g., node 202 ₁₂) can carry out storage I/O to andfrom the storage devices on behalf of a user container instance in adifferent node (e.g., node 202 ₁₁). Strictly as one example, if acontainer performs file system operations such as creating a directoryand then stores a file in that directory, the file system operationsinitiated by the user container can be monitored by and/or performed bya node-specific virtual machine (e.g., a control virtual machine or acontainer service machine). The actual I/O operations to be performed onstorage devices in the storage pool are formed by the node-specificvirtual machine as I/O requests and delivered to the storage device ordevices that store the file. File and directory I/O communicated over ashared memory facility is merely one example of managing storage I/Obetween virtual machines. Communication between two or more virtualmachines can be carried out using any known inter-node communicationtechniques. In some cases file I/O is performed over a virtual disk.

The configurations and partitioning as depicted in the foregoing can becombined, reconfigured and/or repartitioned. FIG. 7B3 illustrates anexample approach that can be taken in some embodiments to process I/Orequests using control VMs that receive storage I/O raised by anexecutable container. The shown flow 7B300 implements a multi-nodestorage I/O transaction using two nodes that share a common memory space(e.g., using a shared memory bus or remote direct memory access or otherprotocol). The flow commences by configuring a first node to host acontrol virtual machine (step 791), and also configuring a second nodeto host an executable container (step 792). The executable containerwrites a storage I/O command to a memory area that is shared by thefirst node and the second node (step 793). Using any know technique, thecontrol virtual machine is notified of the existence of the writtenstorage I/O command, after which notification the control virtualmachine reads the written storage command from the memory area that isshared by the first node and the second node (step 794). The controlvirtual machine hosted on the first node processes the read storagecommand (step 795), which processing includes initiating actionspertaining to the storage I/O command so as to cause processing of oneor more storage operations by storage devices in the storage pool (step796).

Various shared memory access techniques support zero-copy networking byenabling a network switch or network router or other adapter to transferdata directly to and/or from node-local memory areas (e.g., memory areasallocated by a process running on a node) to and/or from shared memoryareas, thus eliminating the need for the network switch or networkrouter or other adapter to be involved in copying data between sharedmemory and the process-allocated memory areas. Such transfers reduce theprocessing to be done by CPUs and reduces operating system contextswitches as well. Such transfers can be performed in parallel with othersystem operations. When a shared memory access read request or writerequest is performed, send/receive latency is reduced, which in turnfacilitates fast, high volume message transfers as might be demanded bycertain storage I/O operations or combinations thereof. Zero-copynetworking can be used when creating and/or accessing virtual disks.

FIG. 7C includes a shared vDisk 170. A vDisk can either be unshared(read and written by a single user VM) or shared (accessed by multipleuser VMs or hypervisors). FIG. 7C illustrates a vDisk in a shared vDiskscenario. More specifically, the vDisk 170 can be accessed by any one ormore of a plurality of operational entities (e.g., containers, VMs,etc.) that are situated on different server nodes (e.g., node 202 ₁₃,node 202 ₁₄). In the example shown, the shared vDisk is owned by ownercontrol virtual machine 130 ₈ on node 202 ₁₄. Therefore, all I/Orequests for vDisk 170 will be directed to this owner control virtualmachine 130 ₈ using standard IP forwarding (network address translationor NAT) rules in the networking stack of the control VMs.

For I/O requests 750 ₄ from a user container instance 252 that resideson the same server as the control virtual machine that owns the targetI/O device (e.g., vDisk), the process to handle the I/O requests 750 ₄is conducted as described above. More specifically, in this embodiment,the I/O request from the user container instance 252 is in the form ofan iSCSI or NFS request that is directed to a given IP address. The IPaddress for the I/O request is common for all the control VMs on thedifferent server nodes, however VLANs allow the IP address of the iSCSIor NFS request to be private to a particular (local) subnet, and hencethe I/O request 750 ₄ will be sent to the owner control virtual machine130 ₈ to handle the I/O request 750 ₄. Since the owner control virtualmachine 130 ₈ recognizes that it is the owner of the vDisk 170, which isthe subject of the I/O request 750 ₄, the owner control virtual machine130 ₈ will directly handle the I/O request 750 ₄.

As another example, consider the situation if a user VM 722 on a servernode issues an I/O request 750 ₃ for the shared vDisk 170, where theshared vDisk is owned by an owning instance of control virtual machine130 ₈ that is running on a different server local control virtualmachine 130 ₇. The local control virtual machine 130 ₇ will recognizethat it is not the owner of the shared vDisk 170, and will furtherrecognize that owner control virtual machine 130 ₈ is the owner of theshared vDisk 170. In this situation, the I/O request will be forwardedfrom local control virtual machine 130 ₇ to control virtual machine 130₈ so that the owner (owner control virtual machine 130 ₈) can handle theforwarded I/O request. To the extent a reply is needed, the reply wouldbe sent to the local control virtual machine 130 ₇ to be forwarded tothe user VM 722 that had originated the I/O request 750 ₃.

In some embodiments, an IP table 724 (e.g., a network address table orNAT) is maintained inside the local control virtual machine 130 ₇. TheIP table 724 is maintained to include the address of remote server VMs.When the local control virtual machine 130 ₇ recognizes that the I/Orequest needs to be sent to another control VM (e.g., owner controlvirtual machine 130 ₈), the IP table 724 is used to look up the addressof the destination control VM. This “NATing” action is performed at thenetwork layers of the OS stack at the local control virtual machine 130₇ whenever the local control virtual machine 130 ₇ decides to send an IPpacket to a control VM other than itself.

FIG. 8 illustrates container uses of VLAN communication techniques 800as used in systems that support configuring, deploying, and managingcontainers in a virtualization environment. As an option, one or morevariations of VLAN communication techniques 800 or any aspect thereofmay be implemented in the context of the architecture and functionalityof the embodiments described herein. The VLAN communication techniques800 or any aspect thereof may be implemented in any environment.

For easy management of the appliance, the control VMs all have the sameaddress (e.g., the same IP address or the same fully-qualified domainname or the same hostname) that is isolated by internal VLANs (virtualLANs in the virtual switch of the hypervisor). FIG. 8 illustrates thisaspect of the architecture. The control virtual machine 130 ₉ on node202 ₁₅ implements two virtual network interface cards (NICs), shown asvirtual NIC 861 ₁ and virtual NIC 861 ₂. One of the virtual NICscorresponds to an internal VLAN that permits the user container virtualmachine 250 ₂ to communicate with the control virtual machine 130 ₉using the common IP address. The virtual switch 702 ₃ routes allcommunications internal to node 202 ₁₅ between the user containervirtual machine 250 ₂ and the control virtual machine 130 ₉ using thefirst instance of virtual NIC 861 ₁, where the common IP address ismanaged to correspond to the control virtual machine 130 ₉ due to itsmembership in the appropriate VLAN.

The second instance of virtual NIC 861 ₂ is used to communicate withentities external to node 202 ₁₅, where the virtual NIC 861 ₂ isassociated with an IP address that would be specific to control virtualmachine 130 ₁₀ (and to no other control VM). The second instance ofvirtual NIC 861 ₂ is therefore used to allow control virtual machine 130₉ to communicate with other control VMs, for example, through virtualswitch 702 ₄, or such as control virtual machine 130 ₁₀ on node 202 ₁₆.It is noted that control virtual machine 130 ₁₀ would likewise use VLANsand multiple virtual NICs (e.g., NIC 861 ₃ and virtual NIC 861 ₄) toimplement management of the appliance.

FIG. 9A and FIG. 9B illustrate alternative embodiments of a controlvirtual machine as used within systems for managing containers in avirtualization environment.

FIG. 9A illustrates the internal structures of a control virtualmachine. In embodiments implementing control VMs as a servicevirtualized computer, the control VMs are not formed in reliance onspecific implementations of hypervisors. Instead, the control VMs run asvirtual machines above hypervisors on the various nodes. Since thecontrol VMs run above the hypervisors, the current approach can be usedand implemented within any virtual machine architecture because thecontrol VMs of embodiments of the invention can be used in conjunctionwith any hypervisor from any virtualization vendor. Therefore, thecontrol VM can be configured to operate ubiquitously anywhere within thecomputing environment, and does not need to be custom-configured foreach different type of operating environment. This is particularlyuseful because the industry-standard iSCSI or NFS protocols allow thecontrol VM to be hypervisor-agnostic.

In some embodiments, the main entry point into a control VM is thecentral controller module (e.g., the I/O director module 904). The termI/O director module is used to connote that fact that this componentdirects the I/O from the world of virtual disks to the pool of physicalstorage resources. In some embodiments, the I/O director moduleimplements the iSCSI or NFS protocol server.

A write request originating at a container service machine is sent tothe iSCSI or NFS target inside the control VM's kernel. This write isthen intercepted by the I/O director module 904 running in user space.The I/O director module 904 interprets the iSCSI LUN or the NFS filedestination and converts the write request into an internal vDiskrequest (e.g., as described in more detail below). Ultimately, the I/Odirector module 904 writes the data to the physical storage.

Each vDisk managed by a control VM corresponds to a virtual addressspace forming the individual bytes exposed as a disk to the containerservice machine. Thus, if the vDisk is 1 terabyte, the correspondingaddress space maintained would be 1 terabyte. This address space isbroken up into equally sized units called vDisk blocks. Metadata 910 ismaintained by the control VM to track and handle the vDisks and the dataand storage objects in the system that pertain to the vDisks. Themetadata 910 is used to track and maintain the contents of the vDisksand vDisk blocks.

To determine where to write and read data from the storage pool, the I/Odirector module 904 communicates with a distributed metadata servicemodule 930 that maintains all the metadata 910. In some embodiments, thedistributed metadata service module 930 is a highly available,fault-tolerant distributed service that runs on all control VMs in theappliance. The metadata managed by distributed metadata service module930 is kept on the persistent storage attached to the appliance.According to some embodiments of the invention, the distributed metadataservice module 930 may be implemented on SSD storage.

Since requests to the distributed metadata service module 930 may berandom in nature, SSDs can be used on each server node to maintain themetadata for the distributed metadata service module 930. Thedistributed metadata service module 930 stores the metadata that helpslocate the actual content of each vDisk block. If no information isfound in distributed metadata service module 930 corresponding to avDisk block, then that vDisk block is assumed to be filled with zeros.The data in each vDisk block is physically stored on disk in contiguousunits called extents. Extents may vary in size when deduplication isbeing used. Otherwise, an extent size coincides with a vDisk block.Several extents are grouped together into a unit called an extent group.An extent group is then stored as a file on disk. The size of eachextent group is anywhere from 16 MB to 64 MB. In some embodiments, anextent group is the unit of recovery, replication, and many otherstorage functions within the system.

A health management module (e.g., curator 908) is employed to addressand remediate or “cure” any inconsistencies that may occur with themetadata 910. The curator 908 oversees the overall state of the virtualstorage system, and takes actions as necessary to manage the health andefficient performance of that system. According to some embodiments ofthe invention, the curator 908 operates on a distributed basis to manageand perform these functions, where a master curator on a first servernode manages the workload that is performed by multiple slave curatorson other server nodes. In some cases map reduce (MR) operations areperformed to implement the curator workload, where the master curatormay periodically coordinate scans of the metadata in the system tomanage the health of the distributed storage system.

Some of the control VMs also include a distributed configurationdatabase module 906 to handle certain administrative tasks. The primarytasks performed by the distributed configuration database module 906 areto maintain the configuration data 912 for the control VM and act as anotification service for all events in the distributed system. Examplesof configuration data 912 include, for example, the identity andexistence of vDisks, the identity of control VMs in the system, thephysical nodes in the system, and the physical storage devices in thesystem. For example, assume that there is a desire to add a new physicaldisk to the storage pool. The distributed configuration database module906 would be informed of the new physical disk, after which theconfiguration data 912 is updated to reflect this information so thatall other entities in the system can be made aware for the new physicaldisk. In a similar way, the addition/deletion of vDisks, VMs and nodesare handled by the distributed configuration database module 906 toupdate the configuration data 912 so that other entities in the systemcan be made aware of these configuration changes.

Another task that is handled by the distributed configuration databasemodule 906 is to maintain health information for entities in the system,such as the control VMs. If a control VM fails or otherwise becomesunavailable, then this module tracks the health information so that anymanagement tasks required of that failed control VM can be migrated toanother control VM.

The distributed configuration database module 906 also handles electionsand consensus management within the system. Another task handled by thedistributed configuration database module is to implement ID creation.Unique IDs are generated by the distributed configuration databasemodule as needed for any required objects in the system (e.g., forvDisks, control VMs, extent groups, etc.). In some embodiments, the IDsgenerated are 64-bit IDs, although any suitable type of IDs can begenerated as appropriate for a particular embodiment. According to someembodiments, the distributed configuration database module may beimplemented on an SSD storage device.

FIG. 9B illustrates the internal structures of the I/O director module904 according to some embodiments of the invention. An iSCSI or NFSadapter 960 is used to convert the incoming/outgoing iSCSI or NFSrequests that are in the iSCSI or NFS format (packet-based format) toinformation that can be used to identify the storage target of therequest. In particular, the incoming/outgoing iSCSI or NFS requests canbe converted into (1) a LUN ID number or (2) a file handle and offset ofthe storage object to be accessed.

If the I/O request is intended to write to a vDisk, then the admissioncontrol module 970 determines whether the control VM is the owner and/oris authorized to write to the particular vDisk identified in the I/Orequest. In some embodiments, a “shared nothing” architecture isimplemented such that only the specific control VM that is listed as theowner of the vDisk is permitted to write to that vDisk. This ownershipinformation may be maintained by distributed configuration databasemodule 906, and can be observed or overridden by the vDisk controller980.

If the control VM is not the owner, the distributed configurationdatabase module 906 is consulted to determine the owner. The owner isthen asked to relinquish ownership so that the current control VM canthen perform the requested I/O operation. If the control VM is theowner, then the requested operation can be immediately processed.

Admission control module 970 can also be used to implement I/Ooptimizations as well. For example, quality of service (QoS)optimizations can be implemented using the admission control module 970.For many reasons, it is desirable to have a storage management systemthat is capable of managing and implementing QoS guarantees. This isbecause many computing and business organizations must be able toguarantee a certain level of service so as to implement a sharedcomputing structure (e.g., to satisfy the contractual obligations ofservice level agreements).

Additional Embodiments of the Disclosure

Additional Practical Application Examples

FIG. 10 depicts a system 1000 as an arrangement of computing modulesthat are interconnected so as to operate cooperatively to implementcertain of the herein-disclosed embodiments. The partitioning of system1000 is merely illustrative and other partitions are possible. FIG. 10depicts a block diagram of a system to perform certain functions of acomputer system. As an option, the system 1000 may be implemented in thecontext of the architecture and functionality of the embodimentsdescribed herein. Of course, however, the system 1000 or any operationtherein may be carried out in any desired environment.

The system 1000 comprises at least one processor and at least onememory, the memory serving to store program instructions correspondingto the operations of the system. As shown, an operation can beimplemented in whole or in part using program instructions accessible bya module. The modules are connected to a communication path 1005, andany operation can communicate with other operations over communicationpath 1005. The modules of the system can, individually or incombination, perform method operations within system 1000. Anyoperations performed within system 1000 may be performed in any orderunless as may be specified in the claims.

The shown embodiment implements a portion of a computer system forconfiguring and managing storage devices, presented as system 1000,comprising a computer processor to execute a set of program codeinstructions (module 1010) and modules for accessing memory to holdprogram code instructions to perform: configuring a plurality of nodes(module 1020), where a node of the plurality of nodes comprises avirtualized controller and one or more user containers, and where thevirtualized controller is configured to operate as a storage controllerdedicated to the node. Another module serves to configure a plurality ofstorage devices that are accessed by the one or more user containers,the virtualized controller being configured to manage access by the usercontainers to the plurality of storage devices (module 1030).

Variations of the foregoing may include more or fewer of the shownmodules and variations may perform more or fewer (or different) steps,and/or may use data elements in more, or in fewer (or different)operations.

Strictly as examples, some embodiments include:

-   -   Variations where the one or more user containers run above a        hypervisor in a user virtual machine.    -   Variations where an isolated virtual machine running above a        hypervisor in the node, the isolated virtual machine being        configured to run virtualized computers comprising isolated        data, the isolated data not being permanently stored on the user        virtual machine.    -   Variations where the user virtual machine further comprises an        interface module configured to retrieve the isolated data from        the isolated virtual machine in response to a request from the        user containers.    -   Variations where the interface module retrieves the data from        the isolated virtual machine using a TCP/IP interface.    -   Variations where the interface module retrieves the data from        the isolated virtual machine using an iSCSI request.    -   Variations where the control virtual machine manages a virtual        disk that is exposed to the user virtual machine.    -   Variations where the virtual disk corresponds to one or more        block devices or server targets.    -   Variations where a new node that is added to the system        corresponds to a new control virtual machine that acts as the        storage controller for the new node.    -   Variations where a request for storage managed by a second        control virtual machine in a second node is sent from a first        control virtual machine in a first node to the second node to be        handled by the second control virtual machine.    -   Variations where the control virtual machine for each of the        plurality of nodes corresponds to a same IP address or a same        fully-qualified domain name or a same hostname that is isolated        by an internal VLAN.    -   Variations where the control virtual machine comprises an I/O        director module, wherein the I/O director module operates to        intercept a request from a user container through the user        virtual machine and the I/O director module formats the request        into a virtual disk request.    -   Variations where the I/O director module comprises an admission        control module that determines whether the control virtual        machine is permitted to operate upon data storage identified in        a request.    -   Variations where the I/O director module comprises a virtual        disk controller that implements read and write requests.    -   Variations where the control virtual machine comprises a        distributed metadata service module to maintain metadata for        virtual disks managed by the control virtual machine.    -   Variations where the control virtual machine comprises a health        management module to maintain consistency of metadata for        virtual disks managed by the control virtual machine.    -   Variations where the control virtual machine comprises a        distributed configuration database module to maintain        configuration data for the control virtual machine.    -   Variations where the distributed configuration database module        operates to maintain health information for entities in a        system, to handle elections, or to perform consensus management.    -   Variations where the user containers comprise one or more        operating system components.    -   Variations where one or more of the operating system components        comprises an application execution environment such as a set of        Docker modules.

System Architecture Overview

Additional System Architecture Examples

FIG. 11A depicts a virtualized controller as implemented by the shownvirtual machine architecture 11A00. The virtual machine architecturecomprises a collection of interconnected components suitable forimplementing embodiments of the present disclosure and/or for use in theherein-described environments. Moreover, the shown virtual machinearchitecture 11A00 includes a virtual machine instance in aconfiguration 1101 that is further described as pertaining to thecontroller virtual machine instance 1130. A controller virtual machineinstance receives block I/O (input/output or IO) storage requests asnetwork file system (NFS) requests in the form of NFS requests 1102,and/or internet small computer storage interface (iSCSI) block IOrequests in the form of iSCSI requests 1103, and/or Samba file system(SMB) requests in the form of SMB requests 1104. The controller virtualmachine (CVM) instance publishes and responds to an internet protocol(IP) address (e.g., CVM IP address 1110). Various forms of input andoutput (I/O or IO) can be handled by one or more IO control handlerfunctions (see IOCTL functions 1108) that interface to other functionssuch as data IO manager functions 1114 and/or metadata manager functions1122. As shown, the data IO manager functions can include communicationwith a virtual disk configuration manager 1112 and/or can include director indirect communication with any of various block IO functions (e.g.,NFS IO, iSCSI IO, SMB IO, etc.).

In addition to block IO functions, the configuration 1101 supports IO ofany form (e.g., block IO, streaming IO, packet-based IO, HTTP traffic,etc.) through either or both of a user interface (UI) handler such as UIIO handler 1140 and/or through any of a range of application programminginterfaces (APIs), possibly through the shown API IO manager 1145.

The communications link 1115 can be configured to transmit (e.g., send,receive, signal, etc.) any types of communications packets comprisingany organization of data items. The data items can comprise a payloaddata, a destination address (e.g., a destination IP address) and asource address (e.g., a source IP address), and can include variouspacket processing techniques (e.g., tunneling), encodings (e.g.,encryption), and/or formatting of bit fields into fixed-length blocks orinto variable length fields used to populate the payload. In some cases,packet characteristics include a version identifier, a packet or payloadlength, a traffic class, a flow label, etc. In some cases the payloadcomprises a data structure that is encoded and/or formatted to fit intobyte or word boundaries of the packet.

In some embodiments, hard-wired circuitry may be used in place of or incombination with software instructions to implement aspects of thedisclosure. Thus, embodiments of the disclosure are not limited to anyspecific combination of hardware circuitry and/or software. Inembodiments, the term “logic” shall mean any combination of software orhardware that is used to implement all or part of the disclosure.

The term “computer readable medium” or “computer usable medium” as usedherein refers to any medium that participates in providing instructionsto a data processor for execution. Such a medium may take many formsincluding, but not limited to, non-volatile media and volatile media.Non-volatile media includes any non-volatile storage medium, forexample, solid state storage devices (SSDs) or optical or magnetic diskssuch as disk drives or tape drives. Volatile media includes dynamicmemory such as a random access memory. As shown, the controller virtualmachine instance 1130 includes a content cache manager facility 1116that accesses storage locations, possibly including local dynamic randomaccess memory (DRAM) (e.g., through the local memory device access block1118) and/or possibly including accesses to local solid state storage(e.g., through local SSD device access block 1120).

Common forms of computer readable media includes any non-transitorycomputer readable medium, for example, floppy disk, flexible disk, harddisk, magnetic tape, or any other magnetic medium; CD-ROM or any otheroptical medium; punch cards, paper tape, or any other physical mediumwith patterns of holes; or any RAM, PROM, EPROM, FLASH-EPROM, or anyother memory chip or cartridge. Any data can be stored, for example, inany form of external data repository 1131, which in turn can beformatted into any one or more storage areas, and which can compriseparameterized storage accessible by a key (e.g., a filename, a tablename, a block address, an offset address, etc.). An external datarepository 1131 can store any forms of data, and may comprise a storagearea dedicated to storage of metadata pertaining to the stored forms ofdata. In some cases, metadata, can be divided into portions. Suchportions and/or cache copies can be stored in the external storage datarepository and/or in a local storage area (e.g., in local DRAM areasand/or in local SSD areas). Such local storage can be accessed usingfunctions provided by a local metadata storage access block 1124. Theexternal data repository 1131 can be configured using a CVM virtual diskcontroller 1126, which can in turn manage any number or anyconfiguration of virtual disks.

Execution of the sequences of instructions to practice certainembodiments of the disclosure are performed by a one or more instancesof a processing element such as a data processor, or such as a centralprocessing unit (e.g., CPU1, CPU2). According to certain embodiments ofthe disclosure, two or more instances of a configuration 1101 can becoupled by a communications link 1115 (e.g., backplane, LAN, PTSN, wiredor wireless network, etc.) and each instance may perform respectiveportions of sequences of instructions as may be required to practiceembodiments of the disclosure.

The shown computing platform 1106 is interconnected to the Internet 1148through one or more network interface ports (e.g., network interfaceport 1123 ₁ and network interface port 1123 ₂). The configuration 1101can be addressed through one or more network interface ports using an IPaddress. Any operational element within computing platform 1106 canperform sending and receiving operations using any of a range of networkprotocols, possibly including network protocols that send and receivepackets (e.g., network protocol packet 1121 ₁ and network protocolpacket 1121 ₂).

The computing platform 1106 may transmit and receive messages that canbe composed of configuration data, and/or any other forms of data and/orinstructions organized into a data structure (e.g., communicationspackets). In some cases, the data structure includes program codeinstructions (e.g., application code) communicated through Internet 1148and/or through any one or more instances of communications link 1115.Received program code may be processed and/or executed by a CPU as it isreceived and/or program code may be stored in any volatile ornon-volatile storage for later execution. Program code can betransmitted via an upload (e.g., an upload from an access device overthe Internet 1148 to computing platform 1106). Further, program codeand/or results of executing program code can be delivered to aparticular user via a download (e.g., a download from the computingplatform 1106 over the Internet 1148 to an access device).

The configuration 1101 is merely one sample configuration. Otherconfigurations or partitions can include further data processors, and/ormultiple communications interfaces, and/or multiple storage devices,etc. within a partition. For example, a partition can bound a multi-coreprocessor (e.g., possibly including embedded or co-located memory), or apartition can bound a computing cluster having plurality of computingelements, any of which computing elements are connected directly orindirectly to a communications link. A first partition can be configuredto communicate to a second partition. A particular first partition andparticular second partition can be congruent (e.g., in a processingelement array) or can be different (e.g., comprising disjoint sets ofcomponents).

A module as used herein can be implemented using any mix of any portionsof the system memory and any extent of hard-wired circuitry includinghard-wired circuitry embodied as a data processor. Some embodimentsinclude one or more special-purpose hardware components (e.g., powercontrol, logic, sensors, transducers, etc.). A module may include one ormore state machines and/or combinational logic used to implement orfacilitate the operational and/or performance characteristics pertainingto managing containers in a virtualization environment.

Various implementations of the data repository comprise storage mediaorganized to hold a series of records or files such that individualrecords or files are accessed using a name or key (e.g., a primary keyor a combination of keys and/or query clauses). Such files or recordscan be organized into one or more data structures (e.g., data structuresused to implement or facilitate aspects pertaining to managingcontainers in a virtualization environment. Such files or records can bebrought into and/or stored in volatile or non-volatile memory.

FIG. 11B depicts a virtualized controller implemented by a containerizedarchitecture 11B00. The containerized architecture comprises acollection of interconnected components suitable for implementingembodiments of the present disclosure and/or for use in theherein-described environments. Moreover, the shown containerizedarchitecture 11B00 includes a container instance in a configuration 1151that is further described as pertaining to the container instance 1150.The configuration 1151 includes an operating system layer (as shown)that performs addressing functions such as providing access to externalrequestors via an IP address (e.g., “P.Q.R.S”, as shown). Providingaccess to external requestors can include implementing all or portionsof a protocol specification (e.g., “http:”) and possibly handlingport-specific functions.

The operating system layer can perform port forwarding to any container(e.g., container instance 1150). A container instance can be executed bya processor. Runnable portions of a container instance sometimes derivefrom a container image, which in turn might include all, or portions ofany of, a Java archive repository (JAR) and/or its contents, a script orscripts and/or a directory of scripts, a virtual machine configuration,and may include any dependencies therefrom. In some cases a virtualmachine configuration within a container might include an imagecomprising a minimum set of runnable code. Contents of larger librariesand/or code or data that would not be accessed during runtime of thecontainer instance can be omitted from the larger library to form asmaller library composed of only the code or data that would be accessedduring runtime of the container instance. In some cases, start-up timefor a container instance can be much faster than start-up time for avirtual machine instance, at least inasmuch as the container image mightbe much smaller than a respective virtual machine instance. Furthermore,start-up time for a container instance can be much faster than start-uptime for a virtual machine instance, at least inasmuch as the containerimage might have many fewer code and/or data initialization steps toperform than a respective virtual machine instance.

A container (e.g., a Docker container) can be rooted in a directorysystem, and can be accessed by file system commands (e.g., “ls” or “ls-a”, etc.). The container might optionally include operating systemcomponents 1178, however such separate operating system components neednot be provided. Instead, a container can include a runnable instance1158, which is built (e.g., through compilation and linking, orjust-in-time compilation, etc.) to include all of the library andOS-like functions needed for execution of the runnable instance. In somecases, a runnable instance can be built with a virtual diskconfiguration manager, any of a variety of data IO management functions,etc. In some cases, a runnable instance includes code for, and accessto, a container virtual disk controller 1176. Such a container virtualdisk controller can perform any of the functions that the aforementionedCVM virtual disk controller 1126 can perform, yet such a containervirtual disk controller does not rely on a hypervisor or any particularoperating system so as to perform its range of functions.

In some environments multiple containers can be collocated and/or canshare one or more contexts. For example, multiple containers that shareaccess to a virtual disk can be assembled into a pod (e.g., a Kubernetespod). Pods provide sharing mechanisms (e.g., when multiple containersare amalgamated into the scope of a pod) as well as isolation mechanisms(e.g., such that the namespace scope of one pod does not share thenamespace scope of another pod).

In the foregoing specification, the disclosure has been described withreference to specific embodiments thereof. It will however be evidentthat various modifications and changes may be made thereto withoutdeparting from the broader spirit and scope of the disclosure. Forexample, the above-described process flows are described with referenceto a particular ordering of process actions. However, the ordering ofmany of the described process actions may be changed without affectingthe scope or operation of the disclosure. The specification and drawingsare to be regarded in an illustrative sense rather than in a restrictivesense.

What is claimed is:
 1. A non-transitory computer readable medium havingstored thereon a sequence of instructions which, when execute aprocessor causes the processor to perform a set of acts comprising:determining a deployment location for an executable container, thedeployment location comprising a node of a plurality of nodes forming ahyper-converged environment having a virtualized storage resource, thedeployment location being determined using a container service;deploying the executable container to a container service machine at thedeployment location determined by the container service, wherein theexecutable container initiates a storage access input/output (I/O)command; and processing the storage access I/O command initiated by theexecutable container at the deployment location to access thevirtualized storage resource of the hyper-converged environment.
 2. Thecomputer readable medium of claim 1, wherein the container servicecomprises a control virtual machine that manages a virtual diskaccessible using the storage access I/O command initiated by theexecutable container and the virtual disk managed by the containerservice corresponds to a block device or a server target.
 3. Thecomputer readable medium of claim 1, wherein the container serviceaccesses the virtualized storage resource of the hyper-convergedenvironment to process the storage access I/O command, and thevirtualized storage resource of the hyper-converged environment isshared by a plurality of container services.
 4. The computer readablemedium of claim 1, wherein a request for storage managed by a secondcontainer service on a second node is sent from the container service onthe node to the second node to be processed by the second containerservice.
 5. The computer readable medium of claim 1, wherein a pluralityof container services for each of the plurality of nodes corresponds toa same IP address, a same fully-qualified domain name, or a samehostname that is isolated by an internal VLAN.
 6. The computer readablemedium of claim 1, wherein the container service formats the storageaccess I/O command into a request to a virtual disk stored on thevirtualized storage resource of the hyper-converged environment.
 7. Thecomputer readable medium of claim 1, wherein the container servicemaintains metadata for virtual disks managed by the container serviceand the virtualized storage resource of the hyper-converged environmentis accessible to a plurality of user virtual machines.
 8. The computerreadable medium of claim 1, wherein the executable container comprisesan operating system component and the storage access I/O commandinitiated by the executable container is forwarded by the containerservice without modification.
 9. The computer readable medium of claim1, wherein the container service the executable container is part of agroup of executable containers that are deployed at the same node as aswarm.
 10. A method comprising: determining a deployment location for anexecutable container, the deployment location comprising a node of aplurality of nodes forming a hyper-converged environment having avirtualized storage resource, the deployment location being determinedusing a container service; deploying the executable container to acontainer service machine at the deployment location determined by thecontainer service, wherein the executable container initiates a storageaccess input/output (I/O) command; and processing the storage access I/Ocommand initiated by the executable container at the deployment locationto access the virtualized storage resource of the hyper-convergedenvironment.
 11. The method of claim 10, wherein the container servicecomprises a control virtual machine that manages a virtual diskaccessible using the storage access I/O command initiated by theexecutable container and the virtual disk managed by the containerservice corresponds to a block device or a server target.
 12. The methodof claim 10, wherein the container service accesses the virtualizedstorage resource of the hyper-converged environment to process thestorage access I/O command, and the virtualized storage resource of thehyper-converged environment is shared by a plurality of containerservices.
 13. The method of claim 10, wherein a request for storagemanaged by a second container service on a second node is sent from thecontainer service on the node to the second node to be processed by thesecond container service.
 14. The method of claim 10, wherein aplurality of container services for each of the plurality of nodescorresponds to a same IP address, a same fully-qualified domain name, ora same hostname that is isolated by an internal VLAN.
 15. The method ofclaim 10, wherein the container service formats the storage access I/Ocommand into a request to a virtual disk stored on the virtualizedstorage resource of the hyper-converged environment.
 16. The method ofclaim 10, wherein the container service maintains metadata for virtualdisks managed by the container service and the virtualized storageresource of the hyper-converged environment is accessible to a pluralityof user virtual machines.
 17. The method of claim 10, wherein thecontainer service the executable container is part of a group ofexecutable containers that are deployed at the same node as a swarm. 18.A system comprising: a storage medium having stored thereon a sequenceof instructions; and a processor that executes the sequence ofinstructions to perform a set of acts comprising: determining adeployment location for an executable container, the deployment locationcomprising a node of a plurality of nodes forming a hyper-convergedenvironment having a virtualized storage resource, the deploymentlocation being determined using a container service; deploying theexecutable container to a container service machine at the deploymentlocation determined by the container service, wherein the executablecontainer initiates a storage access input/output (I/O) command; andprocessing the storage access I/O command initiated by the executablecontainer at the deployment location to access the virtualized storageresource of the hyper-converged environment.
 19. The system of claim 18,wherein the container service comprises a control virtual machine thatmanages a virtual disk accessible using the storage access I/O commandinitiated by the executable container and the virtual disk managed bythe container service corresponds to a block device or a server target.20. The system of claim 18, wherein the container service accesses thevirtualized storage resource of the hyper-converged environment toprocess the storage access I/O command, and the virtualized storageresource of the hyper-converged environment is shared by a plurality ofcontainer services.
 21. The system of claim 18, wherein a request forstorage managed by a second container service on a second node is sentfrom the container service on the node to the second node to beprocessed by the second container service.
 22. The system of claim 18,wherein a plurality of container services for each of the plurality ofnodes corresponds to a same IP address, a same fully-qualified domainname, or a same hostname that is isolated by an internal VLAN.
 23. Thesystem of claim 18, wherein the container service formats the storageaccess I/O command into a request to a virtual disk stored on thevirtualized storage resource of the hyper-converged environment.
 24. Thesystem of claim 18, wherein the container service maintains metadata forvirtual disks managed by the container service and the virtualizedstorage resource of the hyper-converged environment is accessible to aplurality of user virtual machines.
 25. The system of claim 18, whereinthe executable container comprises an operating system component and thestorage access I/O command initiated by the executable container isforwarded by the container service without modification.